Skip to content

Conversation

@sei-renae
Copy link
Contributor

@sei-renae sei-renae commented Jun 17, 2025

@ahouseholder
Copy link
Contributor

ahouseholder commented Jul 1, 2025

@j---
Copy link
Collaborator

j--- commented Aug 13, 2025

moving the "gathering information" sections to the how to instead of reference like this makes sense to me.

Copy link
Contributor

@ahouseholder ahouseholder left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like the split of Gathering Info off into the HowTo section of the docs. That part is fine.

  1. What I'm left with though is that in docs/reference/decision_points/* there are (at least as of the current commit) no breadcrumbs pointing from the reference doc to the corresponding howto doc.

I suggest leaving something akin to the following behind in each of the relevant reference pages.

!!! tip Gathering Information about Foo

      See this [HowTo](link) for advice on gathering information about the Foo decision point.

Adjust wording to taste, I'm mostly concerned that (a) there is a link to it, and (b) it's probably in a call-out.

  1. In the new "HowTo" pages, I think it would make sense to also include the current version example block somewhere near the top of the page.
python exec="true" idprefix=""
from ssvc.decision_points.ssvc.automatable import LATEST
from ssvc.doc_helpers import example_block

print(example_block(LATEST))

Other than that I can't think of anything else at the moment.

@ahouseholder
Copy link
Contributor

ahouseholder commented Sep 15, 2025

I had previously commented:

Please consider which/whether this PR is intended to address:

If it is, update the resolution keywords in the description accordingly.

After conversations with @sei-renae, I believe this PR, once complete, would resolve #723 and #537, while leaving #522 and #362 as future work. I added closing keywords to the PR description consistent with this observation.

@sei-renae sei-renae marked this pull request as ready for review September 15, 2025 17:47
Copy link
Contributor

@ahouseholder ahouseholder left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I made a few fixes directly before doing this review. There are still a few changes I'd like to see before we finish this per comments that follow.

@ahouseholder ahouseholder marked this pull request as draft September 16, 2025 20:00
@sei-renae sei-renae marked this pull request as ready for review September 16, 2025 20:57
Copy link
Contributor

@sei-vsarvepalli sei-vsarvepalli left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All markdown changes checkout fine.

Copy link
Contributor

@ahouseholder ahouseholder left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A couple previous comments remain unresolved, and I had a couple new ones on this revision. In particular, the sentence fragment in Human Impact is a blocker for merging.

@sei-renae
Copy link
Contributor Author

@ahouseholder I think I got it all this time

@ahouseholder ahouseholder self-assigned this Sep 17, 2025
@ahouseholder ahouseholder merged commit d99e641 into CERTCC:main Sep 17, 2025
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

content/representation Formatting, page layout, syntax, etc.

Projects

None yet

4 participants